fix: add warning when decorators used without tracer initialization #1274
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #1104
When
@agent,@tool, and other decorators are used without callingagentops.init()first, they now provide clear feedback instead of silently failing.Root Cause
The decorator factory checked
if not tracer.initialized:and silently returned the function result without any indication that tracing wasn't happening. This caused confusion because:Solution
Added
_ensure_tracer_initialized()helper that:agentops.init()or setAGENTOPS_AUTO_INIT=trueNew Environment Variable
AGENTOPS_AUTO_INIT=true- When set, decorators will auto-initialize AgentOps with sensible defaults:auto_start_session=Falseinstrument_llm_calls=TrueFiles Changed
agentops/sdk/decorators/factory.py- Add initialization check with warningtests/unit/sdk/test_decorators.py- Add tests for warning behaviorTest Plan